Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1a8ebfa37435f05f8eec31286131089feb6f6408f62a181c84892564b728d7

Tx prefix hash: c3d9f0e8dadb7857e96feb2aa529ff8c6e2b3cc0637d2d336dcce3223705ade7
Tx public key: 1a081b6569983336d6076007eebda79ec1be4a6532ba31af956fb3fc7a87d6ed
Timestamp: 1704594867 Timestamp [UCT]: 2024-01-07 02:34:27 Age [y:d:h:m:s]: 01:018:06:08:06
Block: 929815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274352 RingCT/type: yes/0
Extra: 011a081b6569983336d6076007eebda79ec1be4a6532ba31af956fb3fc7a87d6ed02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae357279c2c0f9a006ed8b517df81cfeb963ee70850dc7a54bf80039d8a7420a 0.600000000000 1387691 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": 929825, "vin": [ { "gen": { "height": 929815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae357279c2c0f9a006ed8b517df81cfeb963ee70850dc7a54bf80039d8a7420a" } } ], "extra": [ 1, 26, 8, 27, 101, 105, 152, 51, 54, 214, 7, 96, 7, 238, 189, 167, 158, 193, 190, 74, 101, 50, 186, 49, 175, 149, 111, 179, 252, 122, 135, 214, 237, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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