Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1dc0755e0ed30e2b127a1050a0cef9b4ffbe2e153a2f915062f80a6b49a1421

Tx prefix hash: 3ac7bbfe4c0beb2b2fba85f7dcae3e213f5ef6796d00518f6136ebba2f2550bd
Tx public key: d49dfaafff2a1f5daba90ab4dcaadba4c94f9be570b6ddec8130d54fcb1cfef2
Timestamp: 1674904359 Timestamp [UCT]: 2023-01-28 11:12:39 Age [y:d:h:m:s]: 02:071:21:02:31
Block: 684565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573009 RingCT/type: yes/0
Extra: 01d49dfaafff2a1f5daba90ab4dcaadba4c94f9be570b6ddec8130d54fcb1cfef20211000000015029cbac000000000000000000

1 output(s) for total of 3.309420208000 dcy

stealth address amount amount idx
00: 5db1a5be3d6cf9ad5b9ae2ce6136e6f8f82e77e3af8d68d38bd5fa96d4d45d9b 3.309420208000 1126819 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": 684575, "vin": [ { "gen": { "height": 684565 } } ], "vout": [ { "amount": 3309420208, "target": { "key": "5db1a5be3d6cf9ad5b9ae2ce6136e6f8f82e77e3af8d68d38bd5fa96d4d45d9b" } } ], "extra": [ 1, 212, 157, 250, 175, 255, 42, 31, 93, 171, 169, 10, 180, 220, 170, 219, 164, 201, 79, 155, 229, 112, 182, 221, 236, 129, 48, 213, 79, 203, 28, 254, 242, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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