Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18015a1fa84c32ef997bb5fa7794a4b003016cc73e748cc3411267a55f3cb019

Tx prefix hash: 30ad0271a21e4025c3e220931e1c7bc431af2c379ce6d6e619f6c9a4924c5115
Tx public key: dc79e08af0f2f0aeb69c44bdf50979b3170637db8dd9e68433085c6907a199e4
Timestamp: 1576411654 Timestamp [UCT]: 2019-12-15 12:07:34 Age [y:d:h:m:s]: 05:154:02:26:34
Block: 27179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1257050 RingCT/type: yes/0
Extra: 01dc79e08af0f2f0aeb69c44bdf50979b3170637db8dd9e68433085c6907a199e402110000002f4943cd9f000000000000000000

1 output(s) for total of 498.821951260000 dcy

stealth address amount amount idx
00: 0785ba032dd84a1c2bdcf549f520ee4c7efe2de7f7c4e9b0b44d275a71aff012 498.821951260000 45096 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": 27189, "vin": [ { "gen": { "height": 27179 } } ], "vout": [ { "amount": 498821951260, "target": { "key": "0785ba032dd84a1c2bdcf549f520ee4c7efe2de7f7c4e9b0b44d275a71aff012" } } ], "extra": [ 1, 220, 121, 224, 138, 240, 242, 240, 174, 182, 156, 68, 189, 245, 9, 121, 179, 23, 6, 55, 219, 141, 217, 230, 132, 51, 8, 92, 105, 7, 161, 153, 228, 2, 17, 0, 0, 0, 47, 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