Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f990fff08e920e6cffd858aea59cae861e77bccb7f4adb785e0cbc2abc844f

Tx prefix hash: 6db2b2236caf33f6dca704ddb842c1e2ad932853d99209f863c66df25c4d8274
Tx public key: 6d00e83ada2dcc48076a743d8d6e09885d30d7341c105a181d0cb380b7cb5225
Timestamp: 1577909684 Timestamp [UTC]: 2020-01-01 20:14:44 Age [y:d:h:m:s]: 06:065:13:18:40
Block: 36587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1455255 RingCT/type: yes/0
Extra: 016d00e83ada2dcc48076a743d8d6e09885d30d7341c105a181d0cb380b7cb52250211000000314ac5aa02000000000000000000

1 output(s) for total of 0.464272471722 xmr

stealth address amount amount idx tag
00: dbd8aff91ad14813404ce6875ab6a84b4fb2ab850aceca6a20aaf74f924de978 0.464272471722 62013 of 0 -

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 dinastycoin-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": 36597, "vin": [ { "gen": { "height": 36587 } } ], "vout": [ { "amount": 464272471722, "target": { "key": "dbd8aff91ad14813404ce6875ab6a84b4fb2ab850aceca6a20aaf74f924de978" } } ], "extra": [ 1, 109, 0, 232, 58, 218, 45, 204, 72, 7, 106, 116, 61, 141, 110, 9, 136, 93, 48, 215, 52, 28, 16, 90, 24, 29, 12, 179, 128, 183, 203, 82, 37, 2, 17, 0, 0, 0, 49, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369