Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37d3a322a54e524d61810e2635e856fbd9539f36884e5e74479f4441fd67b3d3

Tx prefix hash: b6d35f237290908c34b454258face1454eb57f0db640f326bd6ba61dfc839c15
Tx public key: 1b719e78aaec63b033b7c4cf6679cf2e75b158880b24cb10bd315e6e4272458c
Timestamp: 1747049772 Timestamp [UCT]: 2025-05-12 11:36:12 Age [y:d:h:m:s]: 00:185:22:40:07
Block: 1281277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130603 RingCT/type: yes/0
Extra: 011b719e78aaec63b033b7c4cf6679cf2e75b158880b24cb10bd315e6e4272458c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41596b02641b518402bb993b7bcb1d5893e177058be260719fd63632e3c7f79c 0.600000000000 1768676 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": 1281287, "vin": [ { "gen": { "height": 1281277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41596b02641b518402bb993b7bcb1d5893e177058be260719fd63632e3c7f79c" } } ], "extra": [ 1, 27, 113, 158, 120, 170, 236, 99, 176, 51, 183, 196, 207, 102, 121, 207, 46, 117, 177, 88, 136, 11, 36, 203, 16, 189, 49, 94, 110, 66, 114, 69, 140, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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