Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0f681838f4dee2a4cee91ed51f71d7c065ef258e3c887bae2f4b7519d438b5

Tx prefix hash: cf5e18bed6e16df4b02c14471d5d0758c4ae6739ccb6b6edd24d67026ef4522e
Tx public key: d8eb214e3d9bf340759f890add900cecd694054ddfbac977cf8242327fa81c63
Timestamp: 1727588734 Timestamp [UTC]: 2024-09-29 05:45:34 Age [y:d:h:m:s]: 02:047:00:51:16
Block: 1120472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558235 RingCT/type: yes/0
Extra: 01d8eb214e3d9bf340759f890add900cecd694054ddfbac977cf8242327fa81c63021100000002e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6a5c52cdb715770ba6020a9078b45db01ce57f6e1c89eb5bb15cfca6be794fb1 0.000600000000 1602399 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 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": 1120482, "vin": [ { "gen": { "height": 1120472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a5c52cdb715770ba6020a9078b45db01ce57f6e1c89eb5bb15cfca6be794fb1" } } ], "extra": [ 1, 216, 235, 33, 78, 61, 155, 243, 64, 117, 159, 137, 10, 221, 144, 12, 236, 214, 148, 5, 77, 223, 186, 201, 119, 207, 130, 66, 50, 127, 168, 28, 99, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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: