Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50faea572ac2b512bb55567623c927e90f1cede0e1cc914febce673f97121e1a

Tx prefix hash: 1950cb03ea5df829b18de50f1786809592559350c3a09da30e4fa94adb367f3d
Tx public key: 648dc0e6c0b7cd4f947d86fff0e9d444dcf86f39ad5d348882627bfb727bfc87
Timestamp: 1702504063 Timestamp [UCT]: 2023-12-13 21:47:43 Age [y:d:h:m:s]: 01:189:21:55:33
Block: 912504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396756 RingCT/type: yes/0
Extra: 01648dc0e6c0b7cd4f947d86fff0e9d444dcf86f39ad5d348882627bfb727bfc8702110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c27a08eebc14818e0d060e319ee1c632858339f59f0b4b282f6ceb564e3a34e 0.600000000000 1369732 of 15

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": 912514, "vin": [ { "gen": { "height": 912504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c27a08eebc14818e0d060e319ee1c632858339f59f0b4b282f6ceb564e3a34e" } } ], "extra": [ 1, 100, 141, 192, 230, 192, 183, 205, 79, 148, 125, 134, 255, 240, 233, 212, 68, 220, 248, 111, 57, 173, 93, 52, 136, 130, 98, 123, 251, 114, 123, 252, 135, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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