Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07366d3a384bfec1c9255bf90363c263a0332c299dbe2a152f6e60082520b031

Tx prefix hash: 2ee540d74fd67a3e4f5a694a64a073ab3fc1f41a23843653e90eb6b04721033e
Tx public key: 0beeaae7639173da5b4219af017326e54d33f02c1f04910c89f866b5f4afd626
Timestamp: 1711978561 Timestamp [UCT]: 2024-04-01 13:36:01 Age [y:d:h:m:s]: 01:050:10:56:30
Block: 991021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297095 RingCT/type: yes/0
Extra: 010beeaae7639173da5b4219af017326e54d33f02c1f04910c89f866b5f4afd6260211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acb3a35396dcb1c6f1fd7f5e6da83b217697f4ba9efe10fc96cb0f2d0746a70a 0.600000000000 1451353 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": 991031, "vin": [ { "gen": { "height": 991021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acb3a35396dcb1c6f1fd7f5e6da83b217697f4ba9efe10fc96cb0f2d0746a70a" } } ], "extra": [ 1, 11, 238, 170, 231, 99, 145, 115, 218, 91, 66, 25, 175, 1, 115, 38, 229, 77, 51, 240, 44, 31, 4, 145, 12, 137, 248, 102, 181, 244, 175, 214, 38, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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