Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d39dc150456a71d26e9ae49538685b03ca0d074f96b9f220f611076f643a5874

Tx prefix hash: d51fb7beefdb9fa0c242d86eb31a24356378fae6ff69d559a1d1868b9b0701b4
Tx public key: 358dd679bc7488d7a2764ef2f9a8a15ff4db17a34baf2ce6fa4a86bd0e64ac67
Timestamp: 1706179385 Timestamp [UCT]: 2024-01-25 10:43:05 Age [y:d:h:m:s]: 01:057:00:16:50
Block: 942945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301847 RingCT/type: yes/0
Extra: 01358dd679bc7488d7a2764ef2f9a8a15ff4db17a34baf2ce6fa4a86bd0e64ac6702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dbbfd0266126b1f24fd22ec73c1abeb5a33fa2d157e960a19e70e6e240d3b17 0.600000000000 1401125 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": 942955, "vin": [ { "gen": { "height": 942945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dbbfd0266126b1f24fd22ec73c1abeb5a33fa2d157e960a19e70e6e240d3b17" } } ], "extra": [ 1, 53, 141, 214, 121, 188, 116, 136, 215, 162, 118, 78, 242, 249, 168, 161, 95, 244, 219, 23, 163, 75, 175, 44, 230, 250, 74, 134, 189, 14, 100, 172, 103, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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