Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d9ac43b0c645838ede39a8465148d841fdd9a44dc88a1d15b9da5ccc60d6cbe

Tx prefix hash: e5940f374ee7183bfb9af2f5fe428de78f3bc23aa57c5039ca4079fd1142f966
Tx public key: 0ec010c6ea10b44f2f7a13bdcfff0785a9f5a41bbb70527031de9f824d59d918
Timestamp: 1578065138 Timestamp [UCT]: 2020-01-03 15:25:38 Age [y:d:h:m:s]: 05:350:07:32:35
Block: 37807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1398074 RingCT/type: yes/0
Extra: 010ec010c6ea10b44f2f7a13bdcfff0785a9f5a41bbb70527031de9f824d59d9180211000001b7410370dd000000000000000000

1 output(s) for total of 459.971120772000 dcy

stealth address amount amount idx
00: 66dce6235c816dbf6cc4ab8ef48a193e8743950a6a62bab284b8160715fe2443 459.971120772000 64286 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": 37817, "vin": [ { "gen": { "height": 37807 } } ], "vout": [ { "amount": 459971120772, "target": { "key": "66dce6235c816dbf6cc4ab8ef48a193e8743950a6a62bab284b8160715fe2443" } } ], "extra": [ 1, 14, 192, 16, 198, 234, 16, 180, 79, 47, 122, 19, 189, 207, 255, 7, 133, 169, 245, 164, 27, 187, 112, 82, 112, 49, 222, 159, 130, 77, 89, 217, 24, 2, 17, 0, 0, 1, 183, 65, 3, 112, 221, 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