Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 104c2162cb2c493fd881c605b66c340661f278a30f2f5ed138aa541a8f017eb1

Tx prefix hash: 6cd8f8fa32f7ab49f847d8a9d83a3aa2b432093d17a7753d8cc0099a96daee11
Tx public key: ceb69de3a60e3c2505f88e88758777f439369fa340a4a05d49f673880d750703
Timestamp: 1674374651 Timestamp [UCT]: 2023-01-22 08:04:11 Age [y:d:h:m:s]: 02:087:06:31:11
Block: 680175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584030 RingCT/type: yes/0
Extra: 01ceb69de3a60e3c2505f88e88758777f439369fa340a4a05d49f673880d750703021100000001faf35c9c000000000000000000

1 output(s) for total of 3.422140320000 dcy

stealth address amount amount idx
00: 2b4880a900f7a47272ae7df463ae9050c26fca37b8fa98b40d46f9f50f9e7b6e 3.422140320000 1122202 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": 680185, "vin": [ { "gen": { "height": 680175 } } ], "vout": [ { "amount": 3422140320, "target": { "key": "2b4880a900f7a47272ae7df463ae9050c26fca37b8fa98b40d46f9f50f9e7b6e" } } ], "extra": [ 1, 206, 182, 157, 227, 166, 14, 60, 37, 5, 248, 142, 136, 117, 135, 119, 244, 57, 54, 159, 163, 64, 164, 160, 93, 73, 246, 115, 136, 13, 117, 7, 3, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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