Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d838c778d039e0dbd7af08a310b43bc0d0fcef6b8c16592904d83ef2788958dc

Tx prefix hash: 8ecfa3d7d0913026675e0d83ec5eb5a539a512f84fae075132828dc5f8e052c7
Tx public key: e05a729ef3bfb3e889e8328231463132671b71d7764812009f705f1ac9dbde49
Timestamp: 1699839972 Timestamp [UCT]: 2023-11-13 01:46:12 Age [y:d:h:m:s]: 01:139:03:38:41
Block: 890430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360617 RingCT/type: yes/0
Extra: 01e05a729ef3bfb3e889e8328231463132671b71d7764812009f705f1ac9dbde4902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.688074990000 dcy

stealth address amount amount idx
00: b626ef1ff31aba06d2f181c1f1dc125a086ea918f1f4bf90137624b4074a54ba 0.688074990000 1346453 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": 890440, "vin": [ { "gen": { "height": 890430 } } ], "vout": [ { "amount": 688074990, "target": { "key": "b626ef1ff31aba06d2f181c1f1dc125a086ea918f1f4bf90137624b4074a54ba" } } ], "extra": [ 1, 224, 90, 114, 158, 243, 191, 179, 232, 137, 232, 50, 130, 49, 70, 49, 50, 103, 27, 113, 215, 118, 72, 18, 0, 159, 112, 95, 26, 201, 219, 222, 73, 2, 17, 0, 0, 0, 4, 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