Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f81e21f5a694df4e1341f827e385f41170216a8209af428db566bba455e3b1

Tx prefix hash: 4f10920d04589fe4ce826546e94a81b5a2da41fc7920a1b82cb8f0d3c8db9317
Tx public key: ea935c964e4683bfe51d1f67f880a123173ef897349ea13e89d9c826d180c01b
Timestamp: 1746161318 Timestamp [UCT]: 2025-05-02 04:48:38 Age [y:d:h:m:s]: 00:210:02:26:44
Block: 1273924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147887 RingCT/type: yes/0
Extra: 01ea935c964e4683bfe51d1f67f880a123173ef897349ea13e89d9c826d180c01b0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0864b1013dbc28b5e4a0bb4a157c2bd21e3db45578ea88d70fd283bd322cdf8 0.600000000000 1761211 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": 1273934, "vin": [ { "gen": { "height": 1273924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0864b1013dbc28b5e4a0bb4a157c2bd21e3db45578ea88d70fd283bd322cdf8" } } ], "extra": [ 1, 234, 147, 92, 150, 78, 70, 131, 191, 229, 29, 31, 103, 248, 128, 161, 35, 23, 62, 248, 151, 52, 158, 161, 62, 137, 217, 200, 38, 209, 128, 192, 27, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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