Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b820153e39f1ec103c3e50cc4b61f384544fa4790708f15161f5af55e4db6f4b

Tx prefix hash: a97bf32cd8efc87f62b1cc4cb9af5f50cc0b772e6baee3934a0ea41aba9cd57f
Tx public key: bff8403b39fed7f871182e729f1e1e427ed68d6b84d75690a2090a166f5e8a26
Timestamp: 1635598370 Timestamp [UCT]: 2021-10-30 12:52:50 Age [y:d:h:m:s]: 04:002:07:01:43
Block: 363638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1038511 RingCT/type: yes/0
Extra: 01bff8403b39fed7f871182e729f1e1e427ed68d6b84d75690a2090a166f5e8a2602110000000406faf294000000000000000000

1 output(s) for total of 38.292767626000 dcy

stealth address amount amount idx
00: 73e1544f06e2b3e329aed3cb9b0db7a82aaef5322e49718b58c963b10c07ae81 38.292767626000 739012 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": 363648, "vin": [ { "gen": { "height": 363638 } } ], "vout": [ { "amount": 38292767626, "target": { "key": "73e1544f06e2b3e329aed3cb9b0db7a82aaef5322e49718b58c963b10c07ae81" } } ], "extra": [ 1, 191, 248, 64, 59, 57, 254, 215, 248, 113, 24, 46, 114, 159, 30, 30, 66, 126, 214, 141, 107, 132, 215, 86, 144, 162, 9, 10, 22, 111, 94, 138, 38, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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