Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: baee391e2a7b2ea38e5b94aa2cd2032e880f9df2eb15606cd651023be2303186

Tx prefix hash: 10d63480aac1ce6494b25c949299cd4c6e7f638262e43f5786d6c97804f94c50
Tx public key: 91fbfe652c8c50ac6e54ce8add431d768e2cce2902e8d642a990a4f8fcb9e614
Timestamp: 1735707104 Timestamp [UCT]: 2025-01-01 04:51:44 Age [y:d:h:m:s]: 00:083:09:16:18
Block: 1187646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59372 RingCT/type: yes/0
Extra: 0191fbfe652c8c50ac6e54ce8add431d768e2cce2902e8d642a990a4f8fcb9e614021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a405ff5a889fc6c1d75e523f547cdba4d2337f55011be5fca0e2ece74e2e3f7 0.600000000000 1674139 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1187656, "vin": [ { "gen": { "height": 1187646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a405ff5a889fc6c1d75e523f547cdba4d2337f55011be5fca0e2ece74e2e3f7" } } ], "extra": [ 1, 145, 251, 254, 101, 44, 140, 80, 172, 110, 84, 206, 138, 221, 67, 29, 118, 142, 44, 206, 41, 2, 232, 214, 66, 169, 144, 164, 248, 252, 185, 230, 20, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8