Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b3ddd43c05f40d49bc33450d85fbbb9e2559247868f6a922945d4ba7e80a30b

Tx prefix hash: 4bd0dacec79168cf124933b7055b7aefadabb5db414b7fcd01fed5b2d53d9d70
Tx public key: 9982d03de991b3ac9ecbb542eb61ff7e5219a023467716f2d8d8a24308c35a09
Timestamp: 1718946316 Timestamp [UCT]: 2024-06-21 05:05:16 Age [y:d:h:m:s]: 00:292:04:27:00
Block: 1048834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208778 RingCT/type: yes/0
Extra: 019982d03de991b3ac9ecbb542eb61ff7e5219a023467716f2d8d8a24308c35a090211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 379dbdfcc3fbdd1968fb4fd4cb8ad82abd89251e54cc4488e314b2a786dd5dd7 0.600000000000 1518921 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": 1048844, "vin": [ { "gen": { "height": 1048834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "379dbdfcc3fbdd1968fb4fd4cb8ad82abd89251e54cc4488e314b2a786dd5dd7" } } ], "extra": [ 1, 153, 130, 208, 61, 233, 145, 179, 172, 158, 203, 181, 66, 235, 97, 255, 126, 82, 25, 160, 35, 70, 119, 22, 242, 216, 216, 162, 67, 8, 195, 90, 9, 2, 17, 0, 0, 0, 2, 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