Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7c9416efac2c70ea7226462b89aaa196bc76024cd89f5627e48974c0199996

Tx prefix hash: a486bece956d5d5b6da6524a48bc9d5e03c43f3d6160a46431e4bdf1d74f20ab
Tx public key: 1430abf1f654d2f5e94ce7432333dc0bf119b24e05dbef0e1722c059726c4021
Timestamp: 1711109009 Timestamp [UTC]: 2024-03-22 12:03:29 Age [y:d:h:m:s]: 01:351:21:22:12
Block: 983868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510100 RingCT/type: yes/0
Extra: 011430abf1f654d2f5e94ce7432333dc0bf119b24e05dbef0e1722c059726c40210211000000070011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1fa6a4ee320e3d2012469b829343d952f79fc3fa1b3934d8d2e98c446aa354cd 0.000600000000 1444021 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": 983878, "vin": [ { "gen": { "height": 983868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa6a4ee320e3d2012469b829343d952f79fc3fa1b3934d8d2e98c446aa354cd" } } ], "extra": [ 1, 20, 48, 171, 241, 246, 84, 210, 245, 233, 76, 231, 67, 35, 51, 220, 11, 241, 25, 178, 78, 5, 219, 239, 14, 23, 34, 192, 89, 114, 108, 64, 33, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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