Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b9f3847e8b0e7363bf170178163a2097b8259202e5466425c2c57062951d763

Tx prefix hash: fe0348ca8a6ee4c8a69bb3591971e7854386ef41da44e532ed16fd5c9f40eccf
Tx public key: 5aa7c47a5fdb2a4fda699b15c8b18d0fe30de5b643d91869c2882f221400dd8e
Timestamp: 1729537839 Timestamp [UCT]: 2024-10-21 19:10:39 Age [y:d:h:m:s]: 00:209:21:25:34
Block: 1136593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149846 RingCT/type: yes/0
Extra: 015aa7c47a5fdb2a4fda699b15c8b18d0fe30de5b643d91869c2882f221400dd8e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c62c5903bc955409c3da7d13914485325beddc75fe3abe8b4e7ba14a2f769fc 0.600000000000 1619940 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": 1136603, "vin": [ { "gen": { "height": 1136593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c62c5903bc955409c3da7d13914485325beddc75fe3abe8b4e7ba14a2f769fc" } } ], "extra": [ 1, 90, 167, 196, 122, 95, 219, 42, 79, 218, 105, 155, 21, 200, 177, 141, 15, 227, 13, 229, 182, 67, 217, 24, 105, 194, 136, 47, 34, 20, 0, 221, 142, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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