Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ced931143f87f6ef76b1bb9386a0a7b2c86a7a0825a8c044032b956ce5232a01

Tx prefix hash: bb0351ba74760cd54b17fa0c44495fbc6c7f80ff06606bb852a2cde0508ed093
Tx public key: d21c4f4a6912e57513cca0b091100ce8cabf3d9eeb5d2fb6a0181817d81a6dfc
Timestamp: 1577826591 Timestamp [UCT]: 2019-12-31 21:09:51 Age [y:d:h:m:s]: 05:132:05:34:44
Block: 36015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244279 RingCT/type: yes/0
Extra: 01d21c4f4a6912e57513cca0b091100ce8cabf3d9eeb5d2fb6a0181817d81a6dfc02110000005dc3a1a09f000000000000000000

1 output(s) for total of 466.302998283000 dcy

stealth address amount amount idx
00: fede82cfb0f994b3fe3ab1640ee1220034eab81e0b8c0a4134fdfcc194e7a5f8 466.302998283000 60853 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": 36025, "vin": [ { "gen": { "height": 36015 } } ], "vout": [ { "amount": 466302998283, "target": { "key": "fede82cfb0f994b3fe3ab1640ee1220034eab81e0b8c0a4134fdfcc194e7a5f8" } } ], "extra": [ 1, 210, 28, 79, 74, 105, 18, 229, 117, 19, 204, 160, 176, 145, 16, 12, 232, 202, 191, 61, 158, 235, 93, 47, 182, 160, 24, 24, 23, 216, 26, 109, 252, 2, 17, 0, 0, 0, 93, 195, 161, 160, 159, 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