Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdc48486c1dbb27666d7902e031f9a42f400584d58159d42cc318d0161b73c3

Tx prefix hash: d0171be4cdc08b3e0ec375ae9dcbbbdfd558536e5a5329a7b99739bf7603c1b3
Tx public key: b1ae9c1594222085e1c1778faa25e40feedf1bf99cf4ea29fd43558ef2911072
Timestamp: 1699643359 Timestamp [UCT]: 2023-11-10 19:09:19 Age [y:d:h:m:s]: 01:151:17:27:19
Block: 888794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369627 RingCT/type: yes/0
Extra: 01b1ae9c1594222085e1c1778faa25e40feedf1bf99cf4ea29fd43558ef2911072021100000003faf35c9c000000000000000000

1 output(s) for total of 0.696717183000 dcy

stealth address amount amount idx
00: 5cc45a5e3ac7919d02b1f6cd7bd967ec77fdde88eb267ec3e41238e3ec097b36 0.696717183000 1344753 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": 888804, "vin": [ { "gen": { "height": 888794 } } ], "vout": [ { "amount": 696717183, "target": { "key": "5cc45a5e3ac7919d02b1f6cd7bd967ec77fdde88eb267ec3e41238e3ec097b36" } } ], "extra": [ 1, 177, 174, 156, 21, 148, 34, 32, 133, 225, 193, 119, 143, 170, 37, 228, 15, 238, 223, 27, 249, 156, 244, 234, 41, 253, 67, 85, 142, 242, 145, 16, 114, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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