Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfc69614a07ca9d706b7af5fe5217c8d0e74e4af6107a3b47a84d3605cba985b

Tx prefix hash: 2fb94389211e2ab5f5685a07454e63bf307e9be5212f6892fa01048bc28885ec
Tx public key: 8366a44fda4a9a5eea6e480106e5a71521201378a62e41912a133e65593bf404
Timestamp: 1617341419 Timestamp [UCT]: 2021-04-02 05:30:19 Age [y:d:h:m:s]: 04:039:15:01:36
Block: 231631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1048480 RingCT/type: yes/0
Extra: 018366a44fda4a9a5eea6e480106e5a71521201378a62e41912a133e65593bf40402110000000e9c1fbdcc000000000000000000

1 output(s) for total of 104.839735737000 dcy

stealth address amount amount idx
00: f89d9cf2fd96aac9eb7ac6295e9e1818cce933f6d133f8eee275dcc523176d41 104.839735737000 481185 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": 231641, "vin": [ { "gen": { "height": 231631 } } ], "vout": [ { "amount": 104839735737, "target": { "key": "f89d9cf2fd96aac9eb7ac6295e9e1818cce933f6d133f8eee275dcc523176d41" } } ], "extra": [ 1, 131, 102, 164, 79, 218, 74, 154, 94, 234, 110, 72, 1, 6, 229, 167, 21, 33, 32, 19, 120, 166, 46, 65, 145, 42, 19, 62, 101, 89, 59, 244, 4, 2, 17, 0, 0, 0, 14, 156, 31, 189, 204, 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