Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a71f07ca0bf1e9f88f13fb3d2404c5f38092d6e31cc3e1cf4b5ed638ef66a260

Tx prefix hash: 8cf8756579feedce51b60a1fdfe099928f278f5a1afb55d3f931a559f684dd48
Tx public key: 85479445d6874685b029fce9df0232d933f7154ceea1c09556a044262425e8c4
Timestamp: 1744175675 Timestamp [UCT]: 2025-04-09 05:14:35 Age [y:d:h:m:s]: 00:269:15:21:57
Block: 1257479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190522 RingCT/type: yes/0
Extra: 0185479445d6874685b029fce9df0232d933f7154ceea1c09556a044262425e8c40211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7db2fb8327bcbc3bd0867a09f14a9d05017d73aed039c888019a94e8b038f939 0.600000000000 1744602 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": 1257489, "vin": [ { "gen": { "height": 1257479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7db2fb8327bcbc3bd0867a09f14a9d05017d73aed039c888019a94e8b038f939" } } ], "extra": [ 1, 133, 71, 148, 69, 214, 135, 70, 133, 176, 41, 252, 233, 223, 2, 50, 217, 51, 247, 21, 76, 238, 161, 192, 149, 86, 160, 68, 38, 36, 37, 232, 196, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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