Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73139d4095a3e6bcd424b136bd36147db704e9f0d8d2c4ab840245b67494b65e

Tx prefix hash: 48f4b7a33a93463e5612b7b46ad0e639053dfee922a390aa626671a78ad017ae
Tx public key: 8c6106018176fa1d274a1b235451480489c36a00bae5f0309cac8ccbb51b9e17
Timestamp: 1740797043 Timestamp [UCT]: 2025-03-01 02:44:03 Age [y:d:h:m:s]: 00:334:03:05:49
Block: 1229498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236488 RingCT/type: yes/0
Extra: 018c6106018176fa1d274a1b235451480489c36a00bae5f0309cac8ccbb51b9e17021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cac2fbed1abb4ad5c4f3b215dfe59c48a0300a4a6061c423463763dfaf295d73 0.600000000000 1716385 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": 1229508, "vin": [ { "gen": { "height": 1229498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cac2fbed1abb4ad5c4f3b215dfe59c48a0300a4a6061c423463763dfaf295d73" } } ], "extra": [ 1, 140, 97, 6, 1, 129, 118, 250, 29, 39, 74, 27, 35, 84, 81, 72, 4, 137, 195, 106, 0, 186, 229, 240, 48, 156, 172, 140, 203, 181, 27, 158, 23, 2, 17, 0, 0, 0, 7, 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