Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de326ac9c32a97d05b8695b020cb9adc808e23a939c22182949ed6b3069001f5

Tx prefix hash: 9bc2d0c084daba46f9e33cbedc55a58be45f98936a848786242ed9fe225ec674
Tx public key: 9cf7b3d5a39318f1bb80c81c560af14f7d5c221604c1531c73832201d613f356
Timestamp: 1582046981 Timestamp [UCT]: 2020-02-18 17:29:41 Age [y:d:h:m:s]: 04:282:05:17:10
Block: 67681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094027 RingCT/type: yes/0
Extra: 019cf7b3d5a39318f1bb80c81c560af14f7d5c221604c1531c73832201d613f3560211000000064943cd9f000000000000000000

1 output(s) for total of 366.222951449000 dcy

stealth address amount amount idx
00: ff2b2559b0965ac4dde787294a6ac7a06c61e9a0295ef2b380ccc3d8ecc1f2e7 366.222951449000 124640 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": 67691, "vin": [ { "gen": { "height": 67681 } } ], "vout": [ { "amount": 366222951449, "target": { "key": "ff2b2559b0965ac4dde787294a6ac7a06c61e9a0295ef2b380ccc3d8ecc1f2e7" } } ], "extra": [ 1, 156, 247, 179, 213, 163, 147, 24, 241, 187, 128, 200, 28, 86, 10, 241, 79, 125, 92, 34, 22, 4, 193, 83, 28, 115, 131, 34, 1, 214, 19, 243, 86, 2, 17, 0, 0, 0, 6, 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