Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ea2ff43e321971c428b15da107cb57985095e44df96cafa25fc507830e7454

Tx prefix hash: 9021d13c705b3358732890ac4b81ccbff554b4ae89b5a5491d5871fcdc196f0d
Tx public key: d58e8d9a28e17437c1ec70b936ef7df8c646d4b23d91f3221f256f8eb3ddb09b
Timestamp: 1723353914 Timestamp [UCT]: 2024-08-11 05:25:14 Age [y:d:h:m:s]: 00:153:00:30:39
Block: 1085361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109473 RingCT/type: yes/0
Extra: 01d58e8d9a28e17437c1ec70b936ef7df8c646d4b23d91f3221f256f8eb3ddb09b021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 245cfe4336012f5a91b56578f425721c04a78a5a71edf42161494f5d276dee1b 0.600000000000 1559930 of 15

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": 1085371, "vin": [ { "gen": { "height": 1085361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "245cfe4336012f5a91b56578f425721c04a78a5a71edf42161494f5d276dee1b" } } ], "extra": [ 1, 213, 142, 141, 154, 40, 225, 116, 55, 193, 236, 112, 185, 54, 239, 125, 248, 198, 70, 212, 178, 61, 145, 243, 34, 31, 37, 111, 142, 179, 221, 176, 155, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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