Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457742374b4a38ede143cef5124149ff8342534224f5c4dddca8096fddb4ef6a

Tx prefix hash: a6f780c80c928115a8f45ee0fb5ecdb69f2fd7276b6f3d2328846e4dbae2f4c9
Tx public key: fe937eefc2f05ed92d9d73fd80ef3fe0a6f236e544f8e55885faf4f3346e5a8b
Timestamp: 1613245345 Timestamp [UCT]: 2021-02-13 19:42:25 Age [y:d:h:m:s]: 03:325:15:53:45
Block: 198203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 991798 RingCT/type: yes/0
Extra: 01fe937eefc2f05ed92d9d73fd80ef3fe0a6f236e544f8e55885faf4f3346e5a8b02110000068657f0ba47000000000000000000

1 output(s) for total of 135.291904008000 dcy

stealth address amount amount idx
00: 9038f41b0e2dd6d88a34077d7c2ae654c67afc63efb679d0a81bf6fa89b89209 135.291904008000 405559 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": 198213, "vin": [ { "gen": { "height": 198203 } } ], "vout": [ { "amount": 135291904008, "target": { "key": "9038f41b0e2dd6d88a34077d7c2ae654c67afc63efb679d0a81bf6fa89b89209" } } ], "extra": [ 1, 254, 147, 126, 239, 194, 240, 94, 217, 45, 157, 115, 253, 128, 239, 63, 224, 166, 242, 54, 229, 68, 248, 229, 88, 133, 250, 244, 243, 52, 110, 90, 139, 2, 17, 0, 0, 6, 134, 87, 240, 186, 71, 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