Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fef0e6b25caa428ac9aeba789114d0efdca57d0a08bfba3d22bf4206cb3c32d

Tx prefix hash: 652f30b2dd4506de850c8e823b38412c67e3d65d35251c4409e35628db5f7a83
Tx public key: f46f83c7c0f4e5b11822f8b3a91e12511d209d69a37db09a2f3e533041f43d0e
Timestamp: 1673054428 Timestamp [UCT]: 2023-01-07 01:20:28 Age [y:d:h:m:s]: 02:138:13:22:53
Block: 669208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620760 RingCT/type: yes/0
Extra: 01f46f83c7c0f4e5b11822f8b3a91e12511d209d69a37db09a2f3e533041f43d0e02110000000252542ceb000000000000000000

1 output(s) for total of 3.720797656000 dcy

stealth address amount amount idx
00: eb2c5341c428e56326084b0b2b823e21df7720c389c962691307b1d5719dbe9e 3.720797656000 1110511 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": 669218, "vin": [ { "gen": { "height": 669208 } } ], "vout": [ { "amount": 3720797656, "target": { "key": "eb2c5341c428e56326084b0b2b823e21df7720c389c962691307b1d5719dbe9e" } } ], "extra": [ 1, 244, 111, 131, 199, 192, 244, 229, 177, 24, 34, 248, 179, 169, 30, 18, 81, 29, 32, 157, 105, 163, 125, 176, 154, 47, 62, 83, 48, 65, 244, 61, 14, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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