Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe193254e3982afe9b1ef8feee4b810d242ea6064a27525b495fafbbb5ecd4b6

Tx prefix hash: 331cb0e15e76f06f02c1a3c5cbf53e20f6fb88da6aa033fa6d6809140e4e9937
Tx public key: 542e72eee94619d35e8df2bd76ae3bb801d0a4f657455758c9cd8d6087fab7c9
Timestamp: 1724087909 Timestamp [UCT]: 2024-08-19 17:18:29 Age [y:d:h:m:s]: 00:097:05:54:23
Block: 1091450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69556 RingCT/type: yes/0
Extra: 01542e72eee94619d35e8df2bd76ae3bb801d0a4f657455758c9cd8d6087fab7c902110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0781e6b099124b34d090da11165898ee1eddbdc1afd58e638be6b0f5390e013f 0.600000000000 1566083 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": 1091460, "vin": [ { "gen": { "height": 1091450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0781e6b099124b34d090da11165898ee1eddbdc1afd58e638be6b0f5390e013f" } } ], "extra": [ 1, 84, 46, 114, 238, 233, 70, 25, 211, 94, 141, 242, 189, 118, 174, 59, 184, 1, 208, 164, 246, 87, 69, 87, 88, 201, 205, 141, 96, 135, 250, 183, 201, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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