Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1cb0f4423ec19384acaca252912f5029fc8b5279d5dfce8d8bd31f7e8348518

Tx prefix hash: 99a49c3664dc6270e84611324dd085b8a85d8174700685f7b59635bce4441bca
Tx public key: f4f2e15fe521a4811ba4f394b8bdbfcfe29a8a16792c1ac57a49704f8e6a904e
Timestamp: 1702375987 Timestamp [UCT]: 2023-12-12 10:13:07 Age [y:d:h:m:s]: 01:332:01:05:08
Block: 911456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496146 RingCT/type: yes/0
Extra: 01f4f2e15fe521a4811ba4f394b8bdbfcfe29a8a16792c1ac57a49704f8e6a904e021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f398dfbea61b5de507d865bb95a73bad4c12e37aef89dc5fc0b41a248fb9398a 0.600000000000 1368660 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": 911466, "vin": [ { "gen": { "height": 911456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f398dfbea61b5de507d865bb95a73bad4c12e37aef89dc5fc0b41a248fb9398a" } } ], "extra": [ 1, 244, 242, 225, 95, 229, 33, 164, 129, 27, 164, 243, 148, 184, 189, 191, 207, 226, 154, 138, 22, 121, 44, 26, 197, 122, 73, 112, 79, 142, 106, 144, 78, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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