Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a36072bd856ac8e714d70bf0b6ed6bee1ce942ebb13897eadcb6700fcf819c3

Tx prefix hash: d274378a6c7c230c9a362c374fcc9f3658af9376c107ae13289027d4f44614b1
Tx public key: 864c1f7d401bd0402a5c6232d8bd88726b8d8e05157cce75add7a4c938474bbe
Timestamp: 1723755760 Timestamp [UCT]: 2024-08-15 21:02:40 Age [y:d:h:m:s]: 00:239:11:07:11
Block: 1088699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171020 RingCT/type: yes/0
Extra: 01864c1f7d401bd0402a5c6232d8bd88726b8d8e05157cce75add7a4c938474bbe021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14722482fd5bda3533f0298a9227f76a0e8ac38d923fe26bfc2f2042c73f183d 0.600000000000 1563316 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": 1088709, "vin": [ { "gen": { "height": 1088699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14722482fd5bda3533f0298a9227f76a0e8ac38d923fe26bfc2f2042c73f183d" } } ], "extra": [ 1, 134, 76, 31, 125, 64, 27, 208, 64, 42, 92, 98, 50, 216, 189, 136, 114, 107, 141, 142, 5, 21, 124, 206, 117, 173, 215, 164, 201, 56, 71, 75, 190, 2, 17, 0, 0, 0, 4, 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