Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6686fd826625bc21236e8aa200de4722cf392a65cee59719201d36118fdb4c0

Tx prefix hash: d480e2d627ed88d178db70dc9da1d9e9219d48032c2cbfabd94fd31fe3159c14
Tx public key: 37916cc088a4a8d339676e0ca6eb684f2f7bae3e874537beefacfc4f213d1a7e
Timestamp: 1726129493 Timestamp [UCT]: 2024-09-12 08:24:53 Age [y:d:h:m:s]: 00:213:13:00:15
Block: 1108365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152466 RingCT/type: yes/0
Extra: 0137916cc088a4a8d339676e0ca6eb684f2f7bae3e874537beefacfc4f213d1a7e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5067f17c018b1b93f481c6fc59a0b3b73389631326790b092a7cd7295ff5343 0.600000000000 1586236 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": 1108375, "vin": [ { "gen": { "height": 1108365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5067f17c018b1b93f481c6fc59a0b3b73389631326790b092a7cd7295ff5343" } } ], "extra": [ 1, 55, 145, 108, 192, 136, 164, 168, 211, 57, 103, 110, 12, 166, 235, 104, 79, 47, 123, 174, 62, 135, 69, 55, 190, 239, 172, 252, 79, 33, 61, 26, 126, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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