Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e583d4cbb1ad330fdf5f034ff513d70f75f85073a9bc357790f7308cb9b43a7d

Tx prefix hash: 499f89a4a6bb6505f86352a2d3ee49326b199b26273b35bd4aa4f330dd9aeed0
Tx public key: 5ff8ad5ac18a3cf6a06fdacaf5ce99d680e7a3e23147d6733ff6298affbf8079
Timestamp: 1635103805 Timestamp [UCT]: 2021-10-24 19:30:05 Age [y:d:h:m:s]: 03:074:15:52:22
Block: 359690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 831740 RingCT/type: yes/0
Extra: 015ff8ad5ac18a3cf6a06fdacaf5ce99d680e7a3e23147d6733ff6298affbf80790211000000218d0de867000000000000000000

1 output(s) for total of 39.464419440000 dcy

stealth address amount amount idx
00: 386e1e3326cce049d61b67a76ed70d576d713546dd71a47ef41a3af05256bf0d 39.464419440000 732363 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": 359700, "vin": [ { "gen": { "height": 359690 } } ], "vout": [ { "amount": 39464419440, "target": { "key": "386e1e3326cce049d61b67a76ed70d576d713546dd71a47ef41a3af05256bf0d" } } ], "extra": [ 1, 95, 248, 173, 90, 193, 138, 60, 246, 160, 111, 218, 202, 245, 206, 153, 214, 128, 231, 163, 226, 49, 71, 214, 115, 63, 246, 41, 138, 255, 191, 128, 121, 2, 17, 0, 0, 0, 33, 141, 13, 232, 103, 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