Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01341520db24f09af1e7bd28a5bf6b4d8e9e47b36d4f7c54fd304dbacb6cab1c

Tx prefix hash: 092bde538155eb39b84e188863158fc1469039b624fe86c67b4cf9b0d1d954b1
Tx public key: 76a86265ef6d73d4a6452f11da539bd01326d7f8e3247987d0a5137224e259cd
Timestamp: 1708872872 Timestamp [UCT]: 2024-02-25 14:54:32 Age [y:d:h:m:s]: 01:043:23:00:13
Block: 965313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292431 RingCT/type: yes/0
Extra: 0176a86265ef6d73d4a6452f11da539bd01326d7f8e3247987d0a5137224e259cd0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f3fc72ca974d29f9818a05e6ab27ec0175ae9a2bc6ded3d9471c1b3957c2a32 0.600000000000 1425062 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": 965323, "vin": [ { "gen": { "height": 965313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f3fc72ca974d29f9818a05e6ab27ec0175ae9a2bc6ded3d9471c1b3957c2a32" } } ], "extra": [ 1, 118, 168, 98, 101, 239, 109, 115, 212, 166, 69, 47, 17, 218, 83, 155, 208, 19, 38, 215, 248, 227, 36, 121, 135, 208, 165, 19, 114, 36, 226, 89, 205, 2, 17, 0, 0, 0, 2, 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