Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c84ca3f4392ef2a49c286410fd93220bc2e497788ce4e50a1b3d93d46237065

Tx prefix hash: f84bb417927f629459fcbe7a978a28611906f8229caedc878098d50abb7e66e4
Tx public key: cdedae1a2dcfe93d0e6b50f4c7e5466ef783b75601d27f145e49a006c9bd417a
Timestamp: 1701058154 Timestamp [UCT]: 2023-11-27 04:09:14 Age [y:d:h:m:s]: 01:168:17:05:05
Block: 900516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381773 RingCT/type: yes/0
Extra: 01cdedae1a2dcfe93d0e6b50f4c7e5466ef783b75601d27f145e49a006c9bd417a021100000002e08532b6000000000000000000

1 output(s) for total of 0.637123273000 dcy

stealth address amount amount idx
00: f51ad87a449831c077dabe8ee5cd3ed9a51441e195d49a48861949df973b5094 0.637123273000 1357021 of 0

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": 900526, "vin": [ { "gen": { "height": 900516 } } ], "vout": [ { "amount": 637123273, "target": { "key": "f51ad87a449831c077dabe8ee5cd3ed9a51441e195d49a48861949df973b5094" } } ], "extra": [ 1, 205, 237, 174, 26, 45, 207, 233, 61, 14, 107, 80, 244, 199, 229, 70, 110, 247, 131, 183, 86, 1, 210, 127, 20, 94, 73, 160, 6, 201, 189, 65, 122, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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