Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e404fabf2c4537d7fb69f662fe5cb8600b7d2d74727afaeb65c832bc26c154

Tx prefix hash: 3b1d52b73e98c74f7f85a878f121c15c8aecda9723e8255edde8dd94ae8af0f1
Tx public key: b18d20630d6c9e3800866f344739b26cf1433160d7146553c6370a912ea30b12
Timestamp: 1672665516 Timestamp [UCT]: 2023-01-02 13:18:36 Age [y:d:h:m:s]: 02:122:21:55:28
Block: 665995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609547 RingCT/type: yes/0
Extra: 01b18d20630d6c9e3800866f344739b26cf1433160d7146553c6370a912ea30b12021100000003faf35c9c000000000000000000

1 output(s) for total of 3.813133939000 dcy

stealth address amount amount idx
00: 9d2d9705ca9b2da4109ce335dd2e96793cea02d2a5e94b1fbf0913b183b32f21 3.813133939000 1107074 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": 666005, "vin": [ { "gen": { "height": 665995 } } ], "vout": [ { "amount": 3813133939, "target": { "key": "9d2d9705ca9b2da4109ce335dd2e96793cea02d2a5e94b1fbf0913b183b32f21" } } ], "extra": [ 1, 177, 141, 32, 99, 13, 108, 158, 56, 0, 134, 111, 52, 71, 57, 178, 108, 241, 67, 49, 96, 215, 20, 101, 83, 198, 55, 10, 145, 46, 163, 11, 18, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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