Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d25c67dcf569be5c844226b4bb3d55fa91c616362e2902882008c16e0dcd09

Tx prefix hash: 6b5883c22d3cb7a4712e5ddba27628da1d39c410b02ee79452a479fe3bb41e8f
Tx public key: 5476d71199f9bd211b5cc0332a355e2179f91573a55fc9fb808a0247f8da2b41
Timestamp: 1674480427 Timestamp [UTC]: 2023-01-23 13:27:07 Age [y:d:h:m:s]: 03:295:23:27:13
Block: 681049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 997103 RingCT/type: yes/0
Extra: 015476d71199f9bd211b5cc0332a355e2179f91573a55fc9fb808a0247f8da2b41021100000001faf35c9c000000000000000000

1 output(s) for total of 0.003399397003 xmr

stealth address amount amount idx tag
00: b12d2ee9aa11557ea2f024b3d035fcd0c98991580cc60ba38966c09cebaccebf 0.003399397003 1123126 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": 681059, "vin": [ { "gen": { "height": 681049 } } ], "vout": [ { "amount": 3399397003, "target": { "key": "b12d2ee9aa11557ea2f024b3d035fcd0c98991580cc60ba38966c09cebaccebf" } } ], "extra": [ 1, 84, 118, 215, 17, 153, 249, 189, 33, 27, 92, 192, 51, 42, 53, 94, 33, 121, 249, 21, 115, 165, 95, 201, 251, 128, 138, 2, 71, 248, 218, 43, 65, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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: