Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86b9cac8cf697444e0e18b9d0c725d71a25809fdcd63ad7b11a7d5efc70615ae

Tx prefix hash: 7d25eadfbde12415c10d428987fc58e5de8a46e604630cb138ba9f78e38e1539
Tx public key: 260449459fe551214377fe8a96e04b16a15e8340f06bf0672ee2360c3a445b26
Timestamp: 1736760260 Timestamp [UTC]: 2025-01-13 09:24:20 Age [y:d:h:m:s]: 01:312:07:11:23
Block: 1196371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487123 RingCT/type: yes/0
Extra: 01260449459fe551214377fe8a96e04b16a15e8340f06bf0672ee2360c3a445b26021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f1f3d167c5402d15564542104ba13036b5d897e8e6e63c47abd74674d418c60 0.000600000000 1682970 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": 1196381, "vin": [ { "gen": { "height": 1196371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f1f3d167c5402d15564542104ba13036b5d897e8e6e63c47abd74674d418c60" } } ], "extra": [ 1, 38, 4, 73, 69, 159, 229, 81, 33, 67, 119, 254, 138, 150, 224, 75, 22, 161, 94, 131, 64, 240, 107, 240, 103, 46, 226, 54, 12, 58, 68, 91, 38, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: