Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9584e736ab8cb580e12383b4419814f72d25e2d4cb7cc071c1dc6bd97bc32203

Tx prefix hash: a5825199ff82b6756b9cb79a41d750b7c81ae232ce02c100492de5e8af1274c4
Tx public key: 9605d377e7a19d6b8e153f6bc3e1d95c429aad6fb171a94b324ab68944e5cb46
Timestamp: 1732414678 Timestamp [UCT]: 2024-11-24 02:17:58 Age [y:d:h:m:s]: 00:127:15:20:48
Block: 1160388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91025 RingCT/type: yes/0
Extra: 019605d377e7a19d6b8e153f6bc3e1d95c429aad6fb171a94b324ab68944e5cb46021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 503f1746a590dc9d192f803471bdf71577a8ab2067eef80e70a91dc2103983f2 0.600000000000 1646035 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": 1160398, "vin": [ { "gen": { "height": 1160388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "503f1746a590dc9d192f803471bdf71577a8ab2067eef80e70a91dc2103983f2" } } ], "extra": [ 1, 150, 5, 211, 119, 231, 161, 157, 107, 142, 21, 63, 107, 195, 225, 217, 92, 66, 154, 173, 111, 177, 113, 169, 75, 50, 74, 182, 137, 68, 229, 203, 70, 2, 17, 0, 0, 0, 2, 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