Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ca20ba2d8d0a19734a91b62927baf36d627665a796e0bb261b0fdb52b01ae2

Tx prefix hash: 4761514f9c61ef923a1c717dfa40c7aba05d4c8ef1e6a4e1fe6a123d992f0c5a
Tx public key: 4cd5dfb6f9f61c5f850c1324087831a0208cd0c627ee9cd142711d3051ef2e32
Timestamp: 1719347861 Timestamp [UCT]: 2024-06-25 20:37:41 Age [y:d:h:m:s]: 00:265:05:16:03
Block: 1052142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189524 RingCT/type: yes/0
Extra: 014cd5dfb6f9f61c5f850c1324087831a0208cd0c627ee9cd142711d3051ef2e320211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f59ee2a0d0fa1978a33f870e1f4f881b876411b6d71a33e61e3f3e18f9f774 0.600000000000 1522463 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": 1052152, "vin": [ { "gen": { "height": 1052142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f59ee2a0d0fa1978a33f870e1f4f881b876411b6d71a33e61e3f3e18f9f774" } } ], "extra": [ 1, 76, 213, 223, 182, 249, 246, 28, 95, 133, 12, 19, 36, 8, 120, 49, 160, 32, 140, 208, 198, 39, 238, 156, 209, 66, 113, 29, 48, 81, 239, 46, 50, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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