Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547d7da26849a604e60ea7f2750e30dfb3ed7eab30045b770fee5a6e5bd2d67a

Tx prefix hash: db70c854aaed9f832b36a6e3dfc77751a558f4a777be876dd0cdffd85c41e5f5
Tx public key: cb4d9829f4bbadb96f94181e3df77241c3717f643cc79978e4519d785a6ebe74
Timestamp: 1726652822 Timestamp [UCT]: 2024-09-18 09:47:02 Age [y:d:h:m:s]: 00:073:20:17:32
Block: 1112702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52811 RingCT/type: yes/0
Extra: 01cb4d9829f4bbadb96f94181e3df77241c3717f643cc79978e4519d785a6ebe74021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: add7f68e6bd727eb839460521a637d4e4712fd4bd84797da0128c47685aa6a5b 0.600000000000 1592117 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": 1112712, "vin": [ { "gen": { "height": 1112702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "add7f68e6bd727eb839460521a637d4e4712fd4bd84797da0128c47685aa6a5b" } } ], "extra": [ 1, 203, 77, 152, 41, 244, 187, 173, 185, 111, 148, 24, 30, 61, 247, 114, 65, 195, 113, 127, 100, 60, 199, 153, 120, 228, 81, 157, 120, 90, 110, 190, 116, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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