Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90ec0dff18b0ff0ecac0cb238aec7ec29575f62bae1176d6c3bc5fb9c2d06ca8

Tx prefix hash: 516e93e4aa88fec9614513966801aef44877b2c65214c9f51e8285880c515ace
Tx public key: 1e3c0b91cb83971ef4a5f3b8b353bc919f7dd0bb0f7cfe1b8c4be7c4428238ab
Timestamp: 1657039778 Timestamp [UCT]: 2022-07-05 16:49:38 Age [y:d:h:m:s]: 03:118:22:28:45
Block: 537296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864714 RingCT/type: yes/0
Extra: 011e3c0b91cb83971ef4a5f3b8b353bc919f7dd0bb0f7cfe1b8c4be7c4428238ab021100000007a8c141c5000000000000000000

1 output(s) for total of 10.179242501000 dcy

stealth address amount amount idx
00: 1e16ede22d4c17020ef4c7ce51dc8b3e8b49d18bfedae7b557dbd4dfd9fa764a 10.179242501000 967169 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": 537306, "vin": [ { "gen": { "height": 537296 } } ], "vout": [ { "amount": 10179242501, "target": { "key": "1e16ede22d4c17020ef4c7ce51dc8b3e8b49d18bfedae7b557dbd4dfd9fa764a" } } ], "extra": [ 1, 30, 60, 11, 145, 203, 131, 151, 30, 244, 165, 243, 184, 179, 83, 188, 145, 159, 125, 208, 187, 15, 124, 254, 27, 140, 75, 231, 196, 66, 130, 56, 171, 2, 17, 0, 0, 0, 7, 168, 193, 65, 197, 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