Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf278551d544e10f4e2935a82efabae45ebf095386ce7182756e762ebc30a12

Tx prefix hash: 41f3be9dc4445df8bb0bb65f78beebceead9afd24133b54a3acb4a906946f6ca
Tx public key: 4051e797022a577e8b2748a89565d6e8d97b78395ae75b14987c9c60a13f9f5b
Timestamp: 1702657676 Timestamp [UCT]: 2023-12-15 16:27:56 Age [y:d:h:m:s]: 01:110:09:42:36
Block: 913777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340031 RingCT/type: yes/0
Extra: 014051e797022a577e8b2748a89565d6e8d97b78395ae75b14987c9c60a13f9f5b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5696cfa0faca279a4028a7e4fb542961b03a7c8849674e9b11c5e0aa67599a44 0.600000000000 1371055 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": 913787, "vin": [ { "gen": { "height": 913777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5696cfa0faca279a4028a7e4fb542961b03a7c8849674e9b11c5e0aa67599a44" } } ], "extra": [ 1, 64, 81, 231, 151, 2, 42, 87, 126, 139, 39, 72, 168, 149, 101, 214, 232, 217, 123, 120, 57, 90, 231, 91, 20, 152, 124, 156, 96, 161, 63, 159, 91, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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