Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f709db821a2ca003451cb13565abf5565a7da3fd8ed55ff22186dd9cb94258

Tx prefix hash: 34255cd676c2378d5e017b7a73cbeb16181d1582dc9c5a0c6d940ab2b6255e1c
Tx public key: d4ed7b274d725d474cd3f6f4fb79d1bf4d0aab0c07fce31304aa13c5366226e5
Timestamp: 1648919361 Timestamp [UTC]: 2022-04-02 17:09:21 Age [y:d:h:m:s]: 04:234:22:33:02
Block: 471767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1211727 RingCT/type: yes/0
Extra: 01d4ed7b274d725d474cd3f6f4fb79d1bf4d0aab0c07fce31304aa13c5366226e50211000000014da16a3a000000000000000000

1 output(s) for total of 0.016781869364 xmr

stealth address amount amount idx tag
00: bcee317652469ad53e736a91fc923d9995e15d0f5e1332a6a7e3ad54350271c1 0.016781869364 891167 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": 471777, "vin": [ { "gen": { "height": 471767 } } ], "vout": [ { "amount": 16781869364, "target": { "key": "bcee317652469ad53e736a91fc923d9995e15d0f5e1332a6a7e3ad54350271c1" } } ], "extra": [ 1, 212, 237, 123, 39, 77, 114, 93, 71, 76, 211, 246, 244, 251, 121, 209, 191, 77, 10, 171, 12, 7, 252, 227, 19, 4, 170, 19, 197, 54, 98, 38, 229, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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) | monero version: