Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88b57daeef72414001a5f19a67fe6f9f933896884e9a2d2f5389f7e0f4fd667

Tx prefix hash: aec273b79e62e238b7e3da5cd631e8161e9995f8123c5c3e03736668ca1246f1
Tx public key: 7bccca723bb82fd1dd3ecc78c631e9e9eef47b2f70b07201e3c72f4a539434f1
Timestamp: 1617596175 Timestamp [UCT]: 2021-04-05 04:16:15 Age [y:d:h:m:s]: 03:336:08:30:18
Block: 233483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 999913 RingCT/type: yes/0
Extra: 017bccca723bb82fd1dd3ecc78c631e9e9eef47b2f70b07201e3c72f4a539434f10211000000043634f08d000000000000000000

1 output(s) for total of 103.367019706000 dcy

stealth address amount amount idx
00: 5a6890baaa7d32e27d678d5ccafcf8c623a67be793f2549a3387c3c6e5290bab 103.367019706000 484879 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": 233493, "vin": [ { "gen": { "height": 233483 } } ], "vout": [ { "amount": 103367019706, "target": { "key": "5a6890baaa7d32e27d678d5ccafcf8c623a67be793f2549a3387c3c6e5290bab" } } ], "extra": [ 1, 123, 204, 202, 114, 59, 184, 47, 209, 221, 62, 204, 120, 198, 49, 233, 233, 238, 244, 123, 47, 112, 176, 114, 1, 227, 199, 47, 74, 83, 148, 52, 241, 2, 17, 0, 0, 0, 4, 54, 52, 240, 141, 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