Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ac378ed9139df466ee45525e22eb9800a1d348db00afb9c36ecdaff03daf6c

Tx prefix hash: 8e59d7470bf756d8182e6c5c95df25abe78d4c0295f0e7c1cf79b081b29aa874
Tx public key: 0358c9fb5e78a36fe557c2e450393d05c81b50c8c01c436a45a3af3a320978ec
Timestamp: 1748333803 Timestamp [UCT]: 2025-05-27 08:16:43 Age [y:d:h:m:s]: 00:171:15:20:57
Block: 1291928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120348 RingCT/type: yes/0
Extra: 010358c9fb5e78a36fe557c2e450393d05c81b50c8c01c436a45a3af3a320978ec021100000002523560da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58b040e0aee2f8386f16fea5b62c8109b824ecf4f57f25491b49dc0002ac2e9c 0.600000000000 1779399 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": 1291938, "vin": [ { "gen": { "height": 1291928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58b040e0aee2f8386f16fea5b62c8109b824ecf4f57f25491b49dc0002ac2e9c" } } ], "extra": [ 1, 3, 88, 201, 251, 94, 120, 163, 111, 229, 87, 194, 228, 80, 57, 61, 5, 200, 27, 80, 200, 192, 28, 67, 106, 69, 163, 175, 58, 50, 9, 120, 236, 2, 17, 0, 0, 0, 2, 82, 53, 96, 218, 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