Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2036247862fa78a0cb57cef28d69faca9d34642f083f06c1caf03ebd2b34c9cb

Tx prefix hash: 5e470b87a19be5b56faee58369e273a32234dc0b012ee8f2e1a1d5623d0b20cb
Tx public key: 22f296fa191d24f950fcf66bdac4aae44185a2ef80d9bafc9d027e754bfff1e8
Timestamp: 1576427572 Timestamp [UCT]: 2019-12-15 16:32:52 Age [y:d:h:m:s]: 04:341:08:22:32
Block: 27835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129648 RingCT/type: yes/0
Extra: 0122f296fa191d24f950fcf66bdac4aae44185a2ef80d9bafc9d027e754bfff1e8021100000003ad433a0b000000000000000000

1 output(s) for total of 496.331633423000 dcy

stealth address amount amount idx
00: 65c09b31e4afc196685e858ff1003ea139ea414e9d8e1c388eaccba3e9a3c14e 496.331633423000 45907 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 dinasty-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": 27845, "vin": [ { "gen": { "height": 27835 } } ], "vout": [ { "amount": 496331633423, "target": { "key": "65c09b31e4afc196685e858ff1003ea139ea414e9d8e1c388eaccba3e9a3c14e" } } ], "extra": [ 1, 34, 242, 150, 250, 25, 29, 36, 249, 80, 252, 246, 107, 218, 196, 170, 228, 65, 133, 162, 239, 128, 217, 186, 252, 157, 2, 126, 117, 75, 255, 241, 232, 2, 17, 0, 0, 0, 3, 173, 67, 58, 11, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8