Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63672be65dee19ad78975e1fc12df8636b161b4c751d26329fdeba5b361f089

Tx prefix hash: 3dfd646787d912074a3949d4de7295f85845eacb84087121aaf88fbfea85b00c
Tx public key: 8bc21dc0f28d3c4b52177639f5191837e3468bf798f78dc662056615f3462caf
Timestamp: 1694396489 Timestamp [UTC]: 2023-09-11 01:41:29 Age [y:d:h:m:s]: 02:244:15:51:53
Block: 845469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686795 RingCT/type: yes/0
Extra: 018bc21dc0f28d3c4b52177639f5191837e3468bf798f78dc662056615f3462caf021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.000969669492 xmr

stealth address amount amount idx tag
00: 05cc121b66c351d5c74dd6493145896105af4534ba3fb7ac3b8ead8e39e5d61a 0.000969669492 1298857 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": 845479, "vin": [ { "gen": { "height": 845469 } } ], "vout": [ { "amount": 969669492, "target": { "key": "05cc121b66c351d5c74dd6493145896105af4534ba3fb7ac3b8ead8e39e5d61a" } } ], "extra": [ 1, 139, 194, 29, 192, 242, 141, 60, 75, 82, 23, 118, 57, 245, 25, 24, 55, 227, 70, 139, 247, 152, 247, 141, 198, 98, 5, 102, 21, 243, 70, 44, 175, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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: