Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e489e8ff5a3a189850b147d4a76e26c5e4d6e6990120ff56a71cfcbe84e6ad6

Tx prefix hash: 10ff25176fdb6d95acee8b9c7f6b6910704d7c4ec5b1febab91d770dc2190d95
Tx public key: fcceb563b158fc3d9d0173cec06df96e38c06b8be024e19c233414c7896eeb90
Timestamp: 1736918587 Timestamp [UCT]: 2025-01-15 05:23:07 Age [y:d:h:m:s]: 00:154:01:20:13
Block: 1197663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109810 RingCT/type: yes/0
Extra: 01fcceb563b158fc3d9d0173cec06df96e38c06b8be024e19c233414c7896eeb9002110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78212900114fc03b3c15849a7f14f2f9372379c7f8db2990949dbcdbdb3e5f65 0.600000000000 1684276 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": 1197673, "vin": [ { "gen": { "height": 1197663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78212900114fc03b3c15849a7f14f2f9372379c7f8db2990949dbcdbdb3e5f65" } } ], "extra": [ 1, 252, 206, 181, 99, 177, 88, 252, 61, 157, 1, 115, 206, 192, 109, 249, 110, 56, 192, 107, 139, 224, 36, 225, 156, 35, 52, 20, 199, 137, 110, 235, 144, 2, 17, 0, 0, 0, 13, 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