Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95561a305be26a11e66f261a565109514607809eec2d537171ccc5ca107a17fe

Tx prefix hash: 6e337e52488e68b9572e4e65a46a94fb60d8cbf23444365e3c463ccd600f90bc
Tx public key: e985d3460513fd07d9f13a1f96e72c8895011ad8a984d2e9cb0f991bb933b190
Timestamp: 1625681131 Timestamp [UCT]: 2021-07-07 18:05:31 Age [y:d:h:m:s]: 03:169:21:43:11
Block: 289869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 891698 RingCT/type: yes/0
Extra: 01e985d3460513fd07d9f13a1f96e72c8895011ad8a984d2e9cb0f991bb933b19002110000048eed79a617000000000000000000

1 output(s) for total of 67.227069142000 dcy

stealth address amount amount idx
00: 1b1441149d3c2e29db5a1297f75375ea567f2e1fa30964fdda408b545b76d408 67.227069142000 607221 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": 289879, "vin": [ { "gen": { "height": 289869 } } ], "vout": [ { "amount": 67227069142, "target": { "key": "1b1441149d3c2e29db5a1297f75375ea567f2e1fa30964fdda408b545b76d408" } } ], "extra": [ 1, 233, 133, 211, 70, 5, 19, 253, 7, 217, 241, 58, 31, 150, 231, 44, 136, 149, 1, 26, 216, 169, 132, 210, 233, 203, 15, 153, 27, 185, 51, 177, 144, 2, 17, 0, 0, 4, 142, 237, 121, 166, 23, 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