Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426ecb78219476cc9fe5a0846144bc8f60f5d4c2832f1a35068ff24fc9931504

Tx prefix hash: 1ed4851e2db6da5a95bb38cf2c18d6c68f73490ab6bdf04741598a4a0f686644
Tx public key: 168cb2806b681db3001cc3b37981f79d4aa72f16210c5e8fdb607861bc1f7f21
Timestamp: 1732280078 Timestamp [UCT]: 2024-11-22 12:54:38 Age [y:d:h:m:s]: 00:001:15:36:19
Block: 1159268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1177 RingCT/type: yes/0
Extra: 01168cb2806b681db3001cc3b37981f79d4aa72f16210c5e8fdb607861bc1f7f21021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 181336325ecd8e797e73bcf8320ff31c64ccf7a5c14ce7fca31f79fa5f1e0dc6 0.600000000000 1644901 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": 1159278, "vin": [ { "gen": { "height": 1159268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "181336325ecd8e797e73bcf8320ff31c64ccf7a5c14ce7fca31f79fa5f1e0dc6" } } ], "extra": [ 1, 22, 140, 178, 128, 107, 104, 29, 179, 0, 28, 195, 179, 121, 129, 247, 157, 74, 167, 47, 22, 33, 12, 94, 143, 219, 96, 120, 97, 188, 31, 127, 33, 2, 17, 0, 0, 0, 6, 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