Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e0550e188cc5ca647abd3a1494dcbefb2f3f6dc1407566e1077882c576a89a

Tx prefix hash: 565f04f3833a693a1f1f95abde23a0fab7f6d3204acb6456b59e505e4311610a
Tx public key: 0c97469e54dd87e3110b3b1cba8a5d0abb619c096525549e9d85deb0dc3f741c
Timestamp: 1583237206 Timestamp [UCT]: 2020-03-03 12:06:46 Age [y:d:h:m:s]: 05:002:00:35:05
Block: 75490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156469 RingCT/type: yes/0
Extra: 010c97469e54dd87e3110b3b1cba8a5d0abb619c096525549e9d85deb0dc3f741c02110000010e0aca7173000000000000000000

1 output(s) for total of 345.041306155000 dcy

stealth address amount amount idx
00: 8cc7e2d7b568c497478d5ff9e01be742d8207041f5cb3904e66af32254bd49c1 345.041306155000 139434 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": 75500, "vin": [ { "gen": { "height": 75490 } } ], "vout": [ { "amount": 345041306155, "target": { "key": "8cc7e2d7b568c497478d5ff9e01be742d8207041f5cb3904e66af32254bd49c1" } } ], "extra": [ 1, 12, 151, 70, 158, 84, 221, 135, 227, 17, 11, 59, 28, 186, 138, 93, 10, 187, 97, 156, 9, 101, 37, 84, 158, 157, 133, 222, 176, 220, 63, 116, 28, 2, 17, 0, 0, 1, 14, 10, 202, 113, 115, 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