Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae75db7f403de653d7debc8abe2fc630b5552dc2c0b905a0ec07a6bbc566bfd4

Tx prefix hash: 9cd19f25117ee0115a8d77716b41360c538c2e7c71ac2476f3a48ad99a63a012
Tx public key: a58a7d630228cf06ab2b4117caefe081d990ef753f8cb16adf2c020fa1a14a98
Timestamp: 1673244156 Timestamp [UCT]: 2023-01-09 06:02:36 Age [y:d:h:m:s]: 02:088:11:13:26
Block: 670777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584909 RingCT/type: yes/0
Extra: 01a58a7d630228cf06ab2b4117caefe081d990ef753f8cb16adf2c020fa1a14a9802110000000371bd5189000000000000000000

1 output(s) for total of 3.676523128000 dcy

stealth address amount amount idx
00: 2469fc9e4f1c4caec989b983616a81c99ede7ce9420be8839746164b89482a77 3.676523128000 1112198 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": 670787, "vin": [ { "gen": { "height": 670777 } } ], "vout": [ { "amount": 3676523128, "target": { "key": "2469fc9e4f1c4caec989b983616a81c99ede7ce9420be8839746164b89482a77" } } ], "extra": [ 1, 165, 138, 125, 99, 2, 40, 207, 6, 171, 43, 65, 23, 202, 239, 224, 129, 217, 144, 239, 117, 63, 140, 177, 106, 223, 44, 2, 15, 161, 161, 74, 152, 2, 17, 0, 0, 0, 3, 113, 189, 81, 137, 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