Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965f6a146716bb7256deb008ba2bee581b55fa539c98077d33f9b71e1b0b4cf2

Tx prefix hash: f2ce45166ed59f34a93f46a83f8009d62c1c4190ce3d5549e01ca9e03e5b8fab
Tx public key: bf6a9f5991a1234f5f214a5608962750dcbfda683e729e4f7f4d3acc7c382d96
Timestamp: 1577665043 Timestamp [UCT]: 2019-12-30 00:17:23 Age [y:d:h:m:s]: 04:332:20:03:06
Block: 34645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126988 RingCT/type: yes/0
Extra: 01bf6a9f5991a1234f5f214a5608962750dcbfda683e729e4f7f4d3acc7c382d960211000000034943cd9f000000000000000000

1 output(s) for total of 471.202502917000 dcy

stealth address amount amount idx
00: 7935821b1faf81d5f475c89d8dbfa4ccbe83955421f68ac128c47cefe6ef3c70 471.202502917000 58337 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": 34655, "vin": [ { "gen": { "height": 34645 } } ], "vout": [ { "amount": 471202502917, "target": { "key": "7935821b1faf81d5f475c89d8dbfa4ccbe83955421f68ac128c47cefe6ef3c70" } } ], "extra": [ 1, 191, 106, 159, 89, 145, 161, 35, 79, 95, 33, 74, 86, 8, 150, 39, 80, 220, 191, 218, 104, 62, 114, 158, 79, 127, 77, 58, 204, 124, 56, 45, 150, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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