Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3b7557f8d1dcbed180ecda8a174f47799e2843e8f69e5054d564d4703c332c4

Tx prefix hash: 409173b52d5722ab8c1c076ad818d0962b104a52991cb226ad88e97d05b6ceab
Tx public key: c84d0f5b52eac4e889a7064a96d52e44f16220a29fc5103c1f95576299fb4de9
Timestamp: 1705673246 Timestamp [UCT]: 2024-01-19 14:07:26 Age [y:d:h:m:s]: 01:037:22:10:31
Block: 938741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288181 RingCT/type: yes/0
Extra: 01c84d0f5b52eac4e889a7064a96d52e44f16220a29fc5103c1f95576299fb4de902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a9292949a9f37fe2e0efe1befadb7ebf30e49354f1060c11fe99a7bca8b3882 0.600000000000 1396819 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": 938751, "vin": [ { "gen": { "height": 938741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a9292949a9f37fe2e0efe1befadb7ebf30e49354f1060c11fe99a7bca8b3882" } } ], "extra": [ 1, 200, 77, 15, 91, 82, 234, 196, 232, 137, 167, 6, 74, 150, 213, 46, 68, 241, 98, 32, 162, 159, 197, 16, 60, 31, 149, 87, 98, 153, 251, 77, 233, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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