Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aab5585b5e757faef37d0d72e6abdb450b3e10eb5dcf21a8b3683424179cf954

Tx prefix hash: 6963a90e78ed2cf33ac4bbf1b45c2f911ee8f4ae25b5ee0cecd08c7f076f6ad6
Tx public key: 5886e8d0f1e8dfb99f812c4a7cf0879941cb696998fd0ca854485b3c61b17ca4
Timestamp: 1717230867 Timestamp [UCT]: 2024-06-01 08:34:27 Age [y:d:h:m:s]: 00:321:01:48:54
Block: 1034603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229475 RingCT/type: yes/0
Extra: 015886e8d0f1e8dfb99f812c4a7cf0879941cb696998fd0ca854485b3c61b17ca40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eb3691250ed79b98805767a97951a35887499f595d52e18754d95febedfa0bd 0.600000000000 1503116 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": 1034613, "vin": [ { "gen": { "height": 1034603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eb3691250ed79b98805767a97951a35887499f595d52e18754d95febedfa0bd" } } ], "extra": [ 1, 88, 134, 232, 208, 241, 232, 223, 185, 159, 129, 44, 74, 124, 240, 135, 153, 65, 203, 105, 105, 152, 253, 12, 168, 84, 72, 91, 60, 97, 177, 124, 164, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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