Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87c1d0429a506f9cbd31e4f8c13c970df52e14ad92bbdb943ae8ceb7f895150e

Tx prefix hash: 0a3811419e5b162f3e2f4285decc659c13e802c7991a586063b089f229eea2b7
Tx public key: 258d437788f76d8aea5d6352eb092531965f5fa4fb8105d2647bf6983d8dbcb5
Timestamp: 1739337854 Timestamp [UCT]: 2025-02-12 05:24:14 Age [y:d:h:m:s]: 00:028:11:51:08
Block: 1217443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20386 RingCT/type: yes/0
Extra: 01258d437788f76d8aea5d6352eb092531965f5fa4fb8105d2647bf6983d8dbcb5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36f60e727993c3b79bda033e2cfb01771efdfd80e84956c661510fff5050487e 0.600000000000 1704256 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": 1217453, "vin": [ { "gen": { "height": 1217443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36f60e727993c3b79bda033e2cfb01771efdfd80e84956c661510fff5050487e" } } ], "extra": [ 1, 37, 141, 67, 119, 136, 247, 109, 138, 234, 93, 99, 82, 235, 9, 37, 49, 150, 95, 95, 164, 251, 129, 5, 210, 100, 123, 246, 152, 61, 141, 188, 181, 2, 17, 0, 0, 0, 2, 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