Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56b1277be2e1dc871bca74a0c10e8361b740de0a9478a0d118a44caeb99bf41

Tx prefix hash: ddb0b4da8c2c1f7b3376131aaf2f4dfdb9da388f3d9f6b3979bae029269f7a7a
Tx public key: 57ae42cc3699a4b0a9754cf9614a17f147e4866e5f4c29253e2ebfecc3a65702
Timestamp: 1578808923 Timestamp [UCT]: 2020-01-12 06:02:03 Age [y:d:h:m:s]: 05:043:12:11:27
Block: 43691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181256 RingCT/type: yes/0
Extra: 0157ae42cc3699a4b0a9754cf9614a17f147e4866e5f4c29253e2ebfecc3a657020211000000094ac5aa02000000000000000000

1 output(s) for total of 439.778933993000 dcy

stealth address amount amount idx
00: ef1f22c7f7f34cb3f6d951f9a79dd4b92151c5302d7bea348ab62302374ad3e8 439.778933993000 79238 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": 43701, "vin": [ { "gen": { "height": 43691 } } ], "vout": [ { "amount": 439778933993, "target": { "key": "ef1f22c7f7f34cb3f6d951f9a79dd4b92151c5302d7bea348ab62302374ad3e8" } } ], "extra": [ 1, 87, 174, 66, 204, 54, 153, 164, 176, 169, 117, 76, 249, 97, 74, 23, 241, 71, 228, 134, 110, 95, 76, 41, 37, 62, 46, 191, 236, 195, 166, 87, 2, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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