Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510ee1b6b9a6adc1dafba174da38e2d8ee61c3ab4f7393c2d3a61906c4206398

Tx prefix hash: a7850ae1282f4d43a69be9a52c6df24f89700c50ca378b6819ff1618f29e217b
Tx public key: 55f87170c5586d8967d04ed6e5674ab20d7bdc782456c872a584f049551ee9f1
Timestamp: 1603729147 Timestamp [UCT]: 2020-10-26 16:19:07 Age [y:d:h:m:s]: 04:134:23:46:03
Block: 144542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091099 RingCT/type: yes/0
Extra: 0155f87170c5586d8967d04ed6e5674ab20d7bdc782456c872a584f049551ee9f1021100001df2f8cbd8e0000000000000000000

1 output(s) for total of 203.738474702000 dcy

stealth address amount amount idx
00: c5fc9765f7c78a6df287dda342fe12da0fcb78dbcc12143842794961aeca4640 203.738474702000 240138 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": 144552, "vin": [ { "gen": { "height": 144542 } } ], "vout": [ { "amount": 203738474702, "target": { "key": "c5fc9765f7c78a6df287dda342fe12da0fcb78dbcc12143842794961aeca4640" } } ], "extra": [ 1, 85, 248, 113, 112, 197, 88, 109, 137, 103, 208, 78, 214, 229, 103, 74, 178, 13, 123, 220, 120, 36, 86, 200, 114, 165, 132, 240, 73, 85, 30, 233, 241, 2, 17, 0, 0, 29, 242, 248, 203, 216, 224, 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