Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f384a16b515c5cfa66b33e6b5fc118d317d6059e2d2894119025faae88a7de8

Tx prefix hash: 7a84818acfacf83fb53d1e4574eacb3b15558d732af64ecd169db7138845bd30
Tx public key: f74005c6680fd413bbecb843b83c37df0fd4de10aeb7bc9773b985445564acc5
Timestamp: 1725639011 Timestamp [UCT]: 2024-09-06 16:10:11 Age [y:d:h:m:s]: 00:212:21:25:22
Block: 1104307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151983 RingCT/type: yes/0
Extra: 01f74005c6680fd413bbecb843b83c37df0fd4de10aeb7bc9773b985445564acc5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6556084a4c25c2f1e32322e9107f2311ad5fd7c880bb2f9a3be30cf9b0354f8 0.600000000000 1581400 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": 1104317, "vin": [ { "gen": { "height": 1104307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6556084a4c25c2f1e32322e9107f2311ad5fd7c880bb2f9a3be30cf9b0354f8" } } ], "extra": [ 1, 247, 64, 5, 198, 104, 15, 212, 19, 187, 236, 184, 67, 184, 60, 55, 223, 15, 212, 222, 16, 174, 183, 188, 151, 115, 185, 133, 68, 85, 100, 172, 197, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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