Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 657f069faa2f8aa908e36e9daa78e2e62027f2109239d3dc43e09b547b77b8b9

Tx prefix hash: ec138de7dc7b10cebe34b1e95d0119e40cd43c47281e7bb6b665e80b86107c68
Tx public key: f3910fafc79070d5e4a1f1f3bd713205b9be1948461753f1131e605536d5e9e5
Timestamp: 1681131142 Timestamp [UCT]: 2023-04-10 12:52:22 Age [y:d:h:m:s]: 01:220:00:33:54
Block: 735558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418709 RingCT/type: yes/0
Extra: 01f3910fafc79070d5e4a1f1f3bd713205b9be1948461753f1131e605536d5e9e5021100000003b3164c24000000000000000000

1 output(s) for total of 2.242803503000 dcy

stealth address amount amount idx
00: 5940a3991ecc34e818ce9545be547d0d91f7280a896e509bde90cfb594af959e 2.242803503000 1181897 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": 735568, "vin": [ { "gen": { "height": 735558 } } ], "vout": [ { "amount": 2242803503, "target": { "key": "5940a3991ecc34e818ce9545be547d0d91f7280a896e509bde90cfb594af959e" } } ], "extra": [ 1, 243, 145, 15, 175, 199, 144, 112, 213, 228, 161, 241, 243, 189, 113, 50, 5, 185, 190, 25, 72, 70, 23, 83, 241, 19, 30, 96, 85, 54, 213, 233, 229, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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