Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4952554a47f8858d922b957df39739a4b72e97f24a083c5b003ffedb80e37b2a

Tx prefix hash: 2b55509224f21362422ceb8b1eb188528ee6adf8ed7eeeab7aecaf05458a84c9
Tx public key: 2ae50574ea33bb1daba5025da3d163ca84422b9b3fb459a4650f72db17a1c4d5
Timestamp: 1736074142 Timestamp [UCT]: 2025-01-05 10:49:02 Age [y:d:h:m:s]: 00:167:17:49:52
Block: 1190696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119523 RingCT/type: yes/0
Extra: 012ae50574ea33bb1daba5025da3d163ca84422b9b3fb459a4650f72db17a1c4d50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f96526fcf63eade593d6eda09f8c174f5cbfebfc8a0087d5f4fcb33f2b8b0210 0.600000000000 1677213 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": 1190706, "vin": [ { "gen": { "height": 1190696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f96526fcf63eade593d6eda09f8c174f5cbfebfc8a0087d5f4fcb33f2b8b0210" } } ], "extra": [ 1, 42, 229, 5, 116, 234, 51, 187, 29, 171, 165, 2, 93, 163, 209, 99, 202, 132, 66, 43, 155, 63, 180, 89, 164, 101, 15, 114, 219, 23, 161, 196, 213, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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