Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f40cfea8e0fb358b97224624b4a255decde82a1da677aec7f24f6784ed80a8

Tx prefix hash: be63512d2685bc07ce8e3e8993dc02b86af01907bcd43e98ba58bcc3a21647c9
Tx public key: 8c1057d9612e1df2cda3f6f458bb14c28aa74c6aae2c454a389b263d4f09b618
Timestamp: 1701665819 Timestamp [UCT]: 2023-12-04 04:56:59 Age [y:d:h:m:s]: 01:341:11:09:37
Block: 905546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502927 RingCT/type: yes/0
Extra: 018c1057d9612e1df2cda3f6f458bb14c28aa74c6aae2c454a389b263d4f09b61802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.613126613000 dcy

stealth address amount amount idx
00: 0ed71ba86ea29c0a155eaac0ec0993ac911a47cbd3dbeea4cae136af5ad6639d 0.613126613000 1362435 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": 905556, "vin": [ { "gen": { "height": 905546 } } ], "vout": [ { "amount": 613126613, "target": { "key": "0ed71ba86ea29c0a155eaac0ec0993ac911a47cbd3dbeea4cae136af5ad6639d" } } ], "extra": [ 1, 140, 16, 87, 217, 97, 46, 29, 242, 205, 163, 246, 244, 88, 187, 20, 194, 138, 167, 76, 106, 174, 44, 69, 74, 56, 155, 38, 61, 79, 9, 182, 24, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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