Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2399394e208de72fd6b7a6cbe0085b2c687842da3d824e04cc1e121a4499be0e

Tx prefix hash: 22b926f9df8e7427ed02c58b591d729fd339c812c1d10f51798c59eb548d5a21
Tx public key: fee1c7493ddca40cfe5ccb9b3ed7dcb43605e1962b520582cbc99ca543a0e89c
Timestamp: 1724987007 Timestamp [UCT]: 2024-08-30 03:03:27 Age [y:d:h:m:s]: 00:262:23:32:26
Block: 1098896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187840 RingCT/type: yes/0
Extra: 01fee1c7493ddca40cfe5ccb9b3ed7dcb43605e1962b520582cbc99ca543a0e89c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f1a045422f70cf6f73e2bafd66be311d6d1d69c704b5010446c7459bb8bc98b 0.600000000000 1574767 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": 1098906, "vin": [ { "gen": { "height": 1098896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f1a045422f70cf6f73e2bafd66be311d6d1d69c704b5010446c7459bb8bc98b" } } ], "extra": [ 1, 254, 225, 199, 73, 61, 220, 164, 12, 254, 92, 203, 155, 62, 215, 220, 180, 54, 5, 225, 150, 43, 82, 5, 130, 203, 201, 156, 165, 67, 160, 232, 156, 2, 17, 0, 0, 0, 5, 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