Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3bd7960b206545f3ab5f66b970201396577564f0f96bd0c4aa76b7c3e3440c7

Tx prefix hash: dbb9dbf9e12b5b267c556f949f8423ca17361cc84515a9fb97963fdff31e027b
Tx public key: 4ecfc5572d7103d461a5b9018033f8c14982267ef841ea8b0001c1f2295e2cec
Timestamp: 1728459974 Timestamp [UCT]: 2024-10-09 07:46:14 Age [y:d:h:m:s]: 00:178:19:40:31
Block: 1127685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127593 RingCT/type: yes/0
Extra: 014ecfc5572d7103d461a5b9018033f8c14982267ef841ea8b0001c1f2295e2cec021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37fbd9eb412edfdc905d8e1f9c22b3e3664cd911962bedc6ac44339e7f18d659 0.600000000000 1610492 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": 1127695, "vin": [ { "gen": { "height": 1127685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37fbd9eb412edfdc905d8e1f9c22b3e3664cd911962bedc6ac44339e7f18d659" } } ], "extra": [ 1, 78, 207, 197, 87, 45, 113, 3, 212, 97, 165, 185, 1, 128, 51, 248, 193, 73, 130, 38, 126, 248, 65, 234, 139, 0, 1, 193, 242, 41, 94, 44, 236, 2, 17, 0, 0, 0, 1, 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