Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa0cf4e55b1bc179c9ce45e0d8f6d0cdb280d081030d819bd03d030c4e00104

Tx prefix hash: 6ba0131962f6cccbec2a4d4a9ba7595b952ed4206fcd3fa05e5bcab014c6cd7f
Tx public key: ca440a7322d07c255b20392063d09e7d1f1b7a2a5490d27a3561bee9b20727ae
Timestamp: 1697090520 Timestamp [UCT]: 2023-10-12 06:02:00 Age [y:d:h:m:s]: 02:024:05:05:10
Block: 867832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536914 RingCT/type: yes/0
Extra: 01ca440a7322d07c255b20392063d09e7d1f1b7a2a5490d27a3561bee9b20727ae0211000000074b8f5122000000000000000000

1 output(s) for total of 0.817586306000 dcy

stealth address amount amount idx
00: bad523dfd170d82eae3a322a7c440cceb97a0f49dc354c1dc2b90cf740d8d1ff 0.817586306000 1322550 of 0

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": 867842, "vin": [ { "gen": { "height": 867832 } } ], "vout": [ { "amount": 817586306, "target": { "key": "bad523dfd170d82eae3a322a7c440cceb97a0f49dc354c1dc2b90cf740d8d1ff" } } ], "extra": [ 1, 202, 68, 10, 115, 34, 208, 124, 37, 91, 32, 57, 32, 99, 208, 158, 125, 31, 27, 122, 42, 84, 144, 210, 122, 53, 97, 190, 233, 178, 7, 39, 174, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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